Centralized Suites for Analog Devices

This feature distributes the connections for analog guest room extensions across several elements, and centralizes all processing on a single IP node in a hospitality environment.

The implementation requires a single IP controller to function as the Hospitality ICP node and one or more analog controllers (Analog Services Unit, Embedded Analog, or AX Controller) to provide connectivity for the analog devices. The Hospitality ICP node handles the processing and management tasks, as it hosts the hotel and motel features, reports, PMS, GSA, and attendant consoles. It also hosts the guest rooms, either directly, as local extensions on the IP controller, or indirectly, as Suite External Hot Desk Users (Suite EHDUs) on one of the analog controllers. To create a Suite EHDU, it is necessary to program the analog room extensions as external hot desk users (EHDUs) and then group them within a suite. The analog extensions, which are typically connected to different controllers, must then be programmed with suite pilot number. Programming instructions are provided below.

Redundant IP Controller

To enhance system availability, you can implement the IP controller on a redundant server platform. This provides the following benefits:

To take advantage of this feature, you need to install MiVoice Business for Industry Standard Services (ISS) software on a fully redundant platform.

Conditions and Feature Interactions

Programming

IP Controller (Hospitality ICP node)

To program an IP controller to support Suite EHDUs for analog devices:

License and Option Selection form

Enter the required number of External Hot Desk User licenses.

Multiline IP Sets ( ) or User and Services Configuration ( ) form

NOTE: Full Service or Multi-Device users can be added on the User and Services Configuration form. Only Full Service users can be added on the Multiline IP Sets form.

For each guest room extension:

Enable the Hot Desk(ing) User option.
Enable the External Hot Desk User License option.
In the "Number" field, enter the directory number for the External Hot Desk User.
In the "Hot Desk User External Dialing Prefix" field, enter the dialable ARS digits of the analog node that will allow a variable number of digits.
In the "Hot Desk User External Number" field, enter the analog device extension number.
Program the "Interconnect number."

CESID Assignment form

For each room extension:

In the "CESID" field, enter a CESID value for the directory number.

NOTE: To ensure consistent emergency call handling, all suite members should be assigned the CESID associated with the suite pilot number.

Class of Service Options form

For each room extension:

Disable "Hot Desk External User – Answer Confirmation"

Enable "Hot Desk External User – Display Internal Calling ID"
Enable "Hot Desk External User – Permanent Login"
Disable "Hot Desk External User – Allow Mid-Call Features"
Disable "Hot Desk External User – Dial Tone upon Call Completion"
Enter the "Hot Desk External User – Remote MWI Enable Feature Access Code"
Enter the "Hot Desk External User – Remote MWI Disable Feature Access Code"

NOTE: The "Hot Desk External Use - Remote MWI Enable | Disable Feature Access Code" settings should match the "Message Waiting - Activate" and "Message Waiting - Deactivate" feature access codes configured on the analog controller.

Suites ( ) or Multi-device Suites ( ) form

To add a new suite, click Add, enter the "Suite Pilot Number" and then click Save.
To add suite members, click Add Member, enter the "Directory Number" and then click Save (if required, program the "Call Delivery Type" and "Message Waiting" settings).

Guest Rooms form

To facilitate management of the suite, click Add, enter the Suite Pilot Number programmed in the previous step as the "Guest Room Number," and then click Save.

Analog Controller

To program an analog controller to support Suite EHDUs for analog devices:

Analog Sets form

For each guest room extension:

In the "Number" field, enter a directory number.
Program the "Circuit Descriptor Index" and "Interconnect Number" fields.
In the "Remote Group Pilot Number" field, enter the suite pilot number.

NOTE: Although the analog extensions must be Full Service users, they do not consume licenses.

This example describes the programming required for a single guest room in a hospitality environment with one IP controller and three analog controllers.

NOTE: The centralized suites use many numbers for a single room and device. To avoid delay when dialing the pilot suite number, it is recommended to maintain a uniform digit length for all the numbers in a system.

The suite can be called by dialing the suite pilot number, 1012. This rings all of the suite members who have been programmed as external hot desk users (EHDUs). The call for the local representation of EHDU 10121 is forwarded to analog node 408, which in turn causes desk phone 1121 to ring.

To place a call from the suite, a user simply goes off hook. The system automatically hotlines to the Remote Group Pilot Number (the suite pilot number) in an attempt to obtain service. The analog node uses Call Recognition Service to identify the EDHU and provide validation that it belongs the suite in question. If this validation is successful, and if the phone has the correct COS, COR and interconnect privileges to be able to call the Remote Group Pilot Number, the caller is presented with dial tone.

NOTE: While outgoing calls use trusted CRS, CRS does not need to be provisioned on the trunks.

If one of the analog controllers becomes unavailable, the devices connected to it also become unavailable. For example, if analog controller 408 goes offline, the desk phone in room 1012 will no longer function. The bedside and bathroom phones remain available for use.

If the IP controller is fully redundant and one of the server modules becomes unavailable for any reason (hardware or software fault, network outage, etc.), the faulty component is bypassed the healthy server module takes over without disrupting service.